assert: optimize partial comparison of two Set
s
#55970
Open
+5
−13
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
We can skip the conversion to an array of the expected items as we're only iterating over them. Using a labelled
continue
should also slightly improve perf as we no longer need to keep afound
boolean value and check its value.I'm also removing the
TODO
that no longer applies (I suggested adding it when there were plans for aassert.includes
method in the PR which have since been abandoned). Lastly I'm using theSafeSet
methods to iterate over theSet
instances to be consistent with how we iterate overMap
instances just a few lines above.